Embedding a software content space for run-time implementation

ABSTRACT

A computer-implemented method for generating user stories for a software product, includes collecting, by a processor, a plurality of requirements, creating, by the processor, a plurality of content space specification files that includes the plurality of requirements, processing, by the processor, the plurality of content space specification files to generate the user stories, defining, by the processor, a content space, and embedding, by the processor, the content space in the software product.

BACKGROUND

The present invention relates to software development, and morespecifically, to systems and methods for embedding a content space intoa software product for use at run-time of the software product.

As part of developing products and applications, particularly softwareproducts and applications, requirements are determined, usually from awide variety of sources, such as stake-holders, strategy people,customers, marketing, industry trends, standards organizations, andmore. Through various channels, a detailed technical plan of activitiesfor the software development team is derived from the requirements,which can interact in complex ways. The process of generating detailedimplementation plans from requirements is subject to errors from varioussources. Multiple concurrent dialogs among teams, making assumptions anddecisions in parallel, can propagate errors, which can become built intothe project plans and the product architecture and or designs. As such,business results such as time to market, development cost, productviability to compete in the marketplace, and the like can affected.

Use cases have long been implemented to organize and itemizerequirements for software products or application software. Use casesbridge the gap between business and market knowledge, and system design,by focusing on the user interactions with the system. The breakdown ofrequirements into use case or line items frequently occurs in parallelwith, and is in dialog with, the architects and design leaders. Duringthe time frame that requirements are collected and analyzed, therequirements are subject to change which must be reflected in the lineitems or use cases. In addition, new requirements are brought up andmust be analyzed and fit with the existing line items or use cases. Somerequirements are eliminated, with corresponding impacts on line items oruse cases. Use cases continue to have problems of various kinds such asquestions of completeness, understandability, uniqueness andmanageability. What is needed is a method for generating user storiesthat leads to less rework, accelerated delivery and better businessvalue, and to embed those user stories into the software product for useat runtime.

SUMMARY

Exemplary embodiments include a computer-implemented method forgenerating user stories for a software product, the method includingcollecting, by a processor, a plurality of requirements, creating, bythe processor, a plurality of content space specification files thatincludes the plurality of requirements, processing, by the processor,the plurality of content space specification files to generate the userstories, defining, by the processor, a content space, and embedding, bythe processor, the content space in the software product.

Additional exemplary embodiments include a computer program product forgenerating user stories for a software product, the computer programproduct including a non-transitory computer readable medium storinginstructions for causing a computer to implement a method. The methodincludes collecting, by a processor, a plurality of requirements,creating, by the processor, a plurality of content space specificationfiles that includes the plurality of requirements, processing, by theprocessor, the plurality of content space specification files togenerate the user stories, defining, by the processor, a content space,and embedding, by the processor, the content space in the softwareproduct.

Additional exemplary embodiments include a system for generating userstories for a software product, the system including a processorconfigured to collect a plurality of requirements, create a plurality ofcontent space specification files that includes the plurality ofrequirements, process the plurality of content space specification filesto generate the user stories, define a content space, embed the contentspace in the software product and output the user stories.

Further exemplary embodiments include a computer-implemented method forgenerating user stories for a software product, the method includingcollecting a plurality of requirements, defining a content spaceincluding a plurality of cells, each cell defining an agile story, eachcell having a plurality of dimensions, creating a plurality of contentspace specification files that includes the plurality of requirements,defining a content space, traversing at least one dimension of each ofthe plurality of cells to generate a user story, embedding the contentspace in the software product and generating reports defining each ofthe user stories.

Additional features and advantages are realized through the techniquesof the present invention. Other embodiments and aspects of the inventionare described in detail herein and are considered a part of the claimedinvention. For a better understanding of the invention with theadvantages and the features, refer to the description and to thedrawings.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The subject matter which is regarded as the invention is particularlypointed out and distinctly claimed in the claims at the conclusion ofthe specification. The forgoing and other features, and advantages ofthe invention are apparent from the following detailed description takenin conjunction with the accompanying drawings in which:

FIG. 1 illustrates a high level block diagram of a system for generatingagile user stories into a content space, which then is embedded into asoftware product;

FIG. 2 illustrates a chart representation of the five exemplarydimensions described herein;

FIG. 3 illustrates the system for integrating content space data basedon a content space in software of FIG. 1, further illustrating thecontent space tool process flow that defines implementation of contentspace data, and embedding the content space into the software product;

FIGS. 4A and 4B illustrate an example of a table that illustrates theattributes that can be attached to each cell in accordance withexemplary embodiments; and

FIG. 5 illustrates an exemplary embodiment of a system in which contentspace embedding can be implemented.

DETAILED DESCRIPTION

In exemplary embodiments, the systems and methods described herein embeda content space within a software product for availability for normaluse at run-time. For illustrative purposes, the systems and methodsdescribed herein are largely discussed in the context of overall systemmanagement software set of products (e.g., Java), associated buildtools, development and test environments and the like. It will beappreciated that the examples described herein can be readily transposedto other software product environments by those skilled in the art.

In exemplary embodiments, the systems and methods described hereinimplement a content space represented internally, shippable and useableat run-time. In addition, the systems and methods described hereinimplement an internal interface for the software product's internalfunctional parts to access the content space at run time (e.g., aninternal callable set of interfaces that are used by product code). Thesystems and methods described herein further obtain and set attributesto each cell in the content space. The attributes are used for variouspurposes by the run-time functions access content space. Some exampleattributes include, but are not limited to: 1) cell category; 2) cellrequirements; 3) development owner; 4) test owner; 5) graphical userinterface (GUI) panel ID; 6) instances needed, and the like. The systemsand methods described herein further integrate a run-time content spacewithin a normal software product build process. In addition, the systemsand methods described herein update the content space definition withinthe software product after the software is installed (similar toupdating other components of the software product).

As described herein, a content space model is implemented for not onlycollecting requirements and generating user stories but also forembedding into the software product. A content space is a way ofrepresenting software content from an outside-in perspective via a setof dimensions. Each of the content space dimensions has values definedin terms of the software itself that concern a particular aspect, suchas information abstraction, function, external interface and run-timeenvironment. The dimension values can represent existing content andalso new content for the software, based on requirements (via contentspace analysis) for a new release. The content space can beprogrammatically traversed, and as this traversal occurs, end-to-endtestable units (termed user stories) are output, each corresponding to aparticular region of the content space and having content spacecoordinates. The set of all output user stories partitions the softwarecontent and the set of all new and changed user stories partitions therelease requirements. The set of all user stories and various subsets(e.g., all Power user stories) are used to compute the content coveragemetric of various scopes.

An example of how a content space can be set up and implemented is nowdiscussed. It will be appreciated that the following example isillustrative of a content space and not limiting.

In exemplary embodiments, the content space can be a five-dimensionalspace (termed either as a ‘software product content space’ or a ‘contentspace’), such that each cell within the content space is an end-to-enduse case (i.e., agile user story). In exemplary embodiments, the systemsand methods described herein can be implemented at various levels ofscale, from individual software components to very large productscomprising hundreds of components to include in the content space andembed into the software product. The five dimensions structure the workas needed by software development (i.e., design, test, projectmanagement), and the requirements serve to define the values used on thedimensions. As such, the exemplary content space servers to bridge therequirements domain and implementation domain.

FIG. 1 illustrates a high level block diagram of a system 100 forgenerating agile user stories into a content space, which then isembedded into a software product. The system 100 outlines and overviewsthe exemplary methods, the blocks for which are described furtherherein. It will be appreciated that each of the summary detailsdescribed herein includes multiple users from each of the two domains,with multiple reviews. The order in which the individual steps areexecuted is not necessarily serial. Changes in requirements oradditional insights happen during a later step can necessitate reworkingthe results from an earlier step.

In exemplary embodiments, content space specification files 105 aregenerated from the various sources in the requirements domain asdescribed herein. As described further herein, the content spacespecification files are generated from various requirements 101. Acontent space tool 110 receives the content specification files 105 toautomatically generate the agile user stories that can be stored in auser story storage medium 115. An additional storage medium 120 can beimplemented to store changes to the specification files 105, or anyother suitable output during the content space generation. Oncegenerated, the agile user stories can be output to any suitable projectmanagement or test management tool 125 implemented by the users in thedevelopment domain.

The system 100 includes several functions, including, but not limitedto: 1) articulating the content space; 2) classifying regions of thecontent space; 3) grouping the regions of the content space; 4)assigning priorities to use cases; and 5) loading the project managementtool 125.

In articulating the content space, requirements are analyzed in terms ofthe five content space dimensions. This analysis results in (withiteration and consensus building) a definition of values for each of thefive dimensions, which is represented in a form that can beprogrammatically processed. In articulating the content space, thesystems and methods described herein address whether all therequirements are represented in the content space, whether each contentspace dimension value is properly defined and agreed upon, and whetherall the dimension values are related to explicit, implicit or futurerequirements.

In classifying the regions of the content space, once the team issatisfied that the content space is defined (i.e., all dimension valuesknown, understood, and reasonably well-defined) and that it doesencompass all the requirements for a selected time-frame, the team nextdecides on how to classify regions of the content space. Throughautomated systems with team decisions, every cell in the content spaceis categorized in a variety of types, including, but not limited to: 1)does not apply to the product; 2) does apply to the product but for somefuture release; 3) is part of the product today (or from some priorrelease) and has no enhancements or changes; 4) is part of the producttoday and is enhanced or changed in some way; and 5) is a new or anenhanced function. The systems and methods described herein determinewhether each content space dimension value is classified, and reviews ofthe results determine correctness.

Following agreement on the content space and categorization of regions,the content space regions are then grouped. Subsets of the content spaceare grouped together into a size which is desirable for projectmanagement and the scale of the product and teams. This step appliesparticularly to the content space regions classified as unchanged andnew or enhanced (changed). The two extremes are; an entire content spacecan grouped into a single output project management work item, or at theother extreme every single content space cell can be output as a singleproject management line item. Essentially every possible grouping inbetween these extremes is also supported. Typically used are groupingall new and changed user stories for a particular platform or groupingspecific sub-variations of a verb.

In exemplary embodiments, there is flexibility in how these regions areselected and how they related to the content space cell classifications.The systems and methods described herein determine whether the groupingis correct and do the groupings properly reflect the tradeoff betweenproject management needs and technical visibility based onclassifications and complexity.

The grouping of content space cells into right sized project managementwork items mostly focused on a new function and an existing andunchanged function. The user (team) can programmatically select thegrouping of content space cells based on many considerations suchoverall content space size, product size, degree of technical difficultyof new function, team size, number of team, and the like. In exemplaryembodiments, individual content cells are use cases (with adjustablegranularity) and the groupings are user functions or user stories.

Based on the relative priorities of requirements, regions of the contentspace (subsets of use cases) are assigned priority values. These can beused to help focus review sessions to ensure the right higher prioritycontent is defined. When loaded into a project management application,the priorities can be used directly by development in agile sprint(iteration) planning The output project management work items are input(e.g., ‘import’) for example, from the user story storage medium 115,into an appropriate project management tool 125.

As described herein, a content space can be defined by five dimensions.In exemplary embodiments, the five dimensions of the content space are,in order: release (time); noun; verb; interface; and platform. The threedimensions, verb, interface and platform, are orthogonal andnoun-specific. That is, an instance of these (e.g., a verb set, aninterface set and a platform set) is defined for each noun of interest.Nouns are the fourth dimension. The combination of a noun and itsassociated 3D space is termed a ‘noun space’. A set of noun spaces at agiven point in time (usually associated with product release) constitutethe definition of the content space for a particular release of aproduct (when the point in time is chosen on a release calendarboundary). Instances a product content space for multiple releasesrepresent the fifth dimension of content space: time.

For illustrative purposes, an example of a software product, ahypothetical browser-based email client is discussed for ease ofdiscussion. It will be appreciated that other products are contemplatedfor which an embedded content space can be implemented.

FIG. 2 illustrates a chart 200 representation of the five exemplarydimensions described herein. As described herein, the five dimensions ofthe content space are, from inner three to out-most: platform 201;interface 202; verb 203; noun 204; and release (time) 205. All of thevalues for the dimensions are derived from the product requirements,either explicit or implicit.

The platform dimension 201 is interpreted broadly to include thehardware, operating system, middle ware, hypervisor, and languageruntime in which the product executes. Generally, meaningful platformelements are determined by each product. As such, the entireprerequisite software stack and hardware is considered. Values of theplatform dimension 201 can include specific releases of each of theseplatform components as needed, or can be more generally specified. Forexample, a platform might be AIX 5.2 or just AIX. Alternatively, theplatform might be Firefox 3.6 or better, or just Firefox. Values caninclude as needed ancillary hardware for storage, networking, hardwaremanagement controllers, firmware, etc. for the full functional systemconfiguration.

The interface dimension 202 has values chosen to identify and separatethe kinds of interfaces that the subject software presents to externalentities; people, other software or hardware. The values can bespecified by type such as Graphical User Interface (GUI), command lineinterface (CLI), and so on. The values can include programmableinterfaces such as web services (e.g. REST) and APIs. Protocols can alsobe specified as values (e.g., IPv6 or MPI (Message Processing Interface)used in super-computing environments).

The verb dimension 203 includes values such as functions or operationsthat are supported by the subject software for a particular noun. Theoperations may be specified at varying levels of granularity, dependingupon the needs of a given set of requirements. For example ‘copy’ or‘create’ might be sufficient. More fine-grained values such ‘copy tolike repository’ and ‘copy to new folder’ can also be used. The decisiondepends on considerations like how new the function is, or how criticalthe different forms of copy are to the product stake-holders (those thatdefine requirements), or how technically difficult to implement.

The noun dimension 204 is an abstract entity presented to externals viathe interface(s). Most software for direct use by people has a number ofsuch abstractions that people manipulate via the functions (verbs)presented by the software. Example nouns for an email client caninclude, but are not limited to: inbox; inbox email; folder; and draftemail. As with values on the above dimensions, there is flexibility inhow coarse-grained or fine-grained the nouns are defined. The rightlevel of noun dimension granularity for a given product and givenrelease depends on the requirements.

The time dimension 205 values include natural values (i.e., discreteunits) which are the releases planned for the product. The content spacefor release n+1 can be various additions and changes relative to therelease n content space. These additions, enhancements and other changesaffect the release n content space by changing the values defined on thevarious dimensions. New nouns, new verbs, new platforms, can all beadded. Enhancements to exiting nouns and verbs are common and definedexplicitly in the n+1 content space.

Because of the way the dimensions are defined, each generated user storyis an end-to-end testable unit of function (sometimes termed ‘FVT-able’,where FVT=Function Verification Test). For example, for an “email”client each user story is a cell in the five-dimensional space withcoordinates of release, noun, verb, interface and platform. For example,“send an email on Firefox via GUI release n” is represented by a 5-tuple{release n, email, send, GUI, Firefox}, as shown in FIG. 2.

FIG. 3 illustrates the system 100 for integrating content space databased on a content space in software of FIG. 1, further illustrating thecontent space tool 110 process flow that defines implementation ofcontent space data, and embedding the content space into the softwareproduct. In exemplary embodiments, parameters are collected from thecontent space specification files 105 at block 305. In addition, anyinput files and content space symbols and filters are also read into thecontent space tool 110. As such, following invocation and initializationof the content space tool 110, the content space specification file(s)105 are read. In addition, the content space specification files 105 areparsed for correctness and various checks are run to help ensureconsistency across the possibly multiple files. This processing includesall the symbols and filters. At block 310, the content space is managed.In exemplary embodiments, grouping and folding are techniques to managecontent space size. The size of a content space is naturally expressedas the number of user stories it contains, or will output if requested.For example, in software products, content space sizes in range ofhundreds to tens of thousands. Average sizes can be in the range of twothousand to twenty thousand. Both folding and grouping can managecontent space size without eliminating (or hiding) detail that needs tobe visible from the user story output file(s) 115.

In grouping user stories, a set of user stories is represented in outputas a single user story. For example all the user stories for platformABC or for function XYZ might be represented by a single output userstory. Grouping does not change the size of a content space. Groupingallows the number of output user stories to be directly managed withouteliminating any details from the CS specification. There is no limit onthe size of a user story group. In exemplary embodiments, grouping iscontrolled by the user by filters in the content space specificationfile 105.

As filtering occurs, when a filter matches a user story and the filterhas any kind of grouping requested, save the user story is saved in abuffer associated with the filter. After all filtering and allnon-grouped user stories are output. The content space tool 110 loopsthrough all the filters that have any kind of grouping. For each filter,the content space tool 110 performs several steps. First, if a simple‘group’ is requested in the filter, the content space tool 110 generatesthe single grouping user story, summary field, description field, andthe like, and writes to output. The content space tool 110 thencontinues to the next filter. If a type of ‘group by’ is requested, thenfor each group by element (e.g., noun, verb, ifc, platform), the contentspace tool 110 builds subsets of the respective values on the dimensionfrom among the buffered user stories. The content space tool 110 thengenerates a single user story group for each cross-dimension subset,generates the description field that itemizes the subset of user storiesfor the group, and writes the user story group.

Folding also reduces the number of output user stories like grouping.But in contrast to grouping, folding reduces the size of the contentspace. Folding reduces the size of the content space by collecting somenumber of dimension element values into a single value (folding operateson the content space itself while grouping operates on user stories).The resulting single value is then used as a dimension element value inplace of the multiple collected values, thereby reducing the size of thecontent space. The single resulting value is termed a folding symbol(fold sym').

As described herein, folding does not eliminate the details from thecontent space specification file. The values collected into a fold symremain in the content space specification file 105, and the folding doneby the fold sym can be toggled on or off. The value-folding can beswitched on and off for each of the noun, verb, interface and platformdimensions independently or all four dimensions together. Hence not onlyare the values still in the spec file, but the content space can also beprocessed again and user stories generated without folding or differentfolding, to see the detail. Folding can include both dimension foldingand value folding.

In exemplary embodiments, the content space tool 110 processes commandline parameters to determine what kinds of folding are requested. If nofold parameter, the content space tool 110 implements the defaultsetting for folding. As the content space specification files 105 areread, the content space tool 110 collects a list of all fold syms, andvalues for each. After all the noun spaces are read from input files,the content space tool 110 invokes a fold function. The content spacetool implements dimension folding first if requested. For each dimensionfor which folding is requested, the dimension is folded to “*” in eachnoun space. If value folding is requested for any dimensions that havenot been folded, the following steps are implemented. If noun valuefolding, the content space tool 110 folds the noun values by removingnouns in value list of a fold sym and replace with single instance ofthe fold sym. For each (remaining) noun space, for each relevantdimension, the content space tool 110 check each dimension value to seeif it is in the value list of a fold sym. If the noun is in the valuelist of the fold sym, then the content space tool 110 removes the valueand adds the fold sym (once only) to the dimension list. If folding hasbeen set off, the content space tool 110 takes no action. The contentspace by default is loaded in this mode. If fold request for the ‘all’or similar, the interface and platform dimensions are folded (as above)and the verb dimension is value-folded for all noun spaces are folded,and the noun dimension is value-folded.

Referring still to FIG. 3, at block 315, each user story is enumeratedin the content space and run through filters to classify and possiblyadd data. At block 320, the user story groups are generated and at block325 show requests and a summary are generated. At block 330, the contentspace data is embedded into a software product as described furtherherein.

In exemplary embodiments, a content space is specified in a form that isprocessed (read) by the content space tool 110 (e.g., an agile userstory generation program). The specification can be split among multiplefiles (e.g., the content space specification files 105), which can beprocessed individually or together. As such, an overall product contentspace can be split among some number of individual architects forparallel concurrent activity, and then processed as a whole.

In exemplary embodiments, each content space specification file 105includes some number of noun spaces, defined symbols, and filters. Acontent space specification file 105 is used to define a content spacein a form that can be processed programmatically. In exemplaryembodiments, the specification file 105 is implemented to generate userstories and provide various kinds of statistics about the content space,enables content coverage metric, automated comparisons of multiplecontent spaces (e.g. cross-release), and the like. In exemplaryembodiments, the content space specification file 105 includes severalstatements, which define, among other things, a noun space, that caninclude noun, verb, interface (ifc) and platform. A content space is aset of noun spaces. As such, a basic content space specification filedefines one or more noun spaces. Descriptive names are used for thevalues on all these dimensions. In exemplary embodiments, additionalstatements can be added to the content space specification file 105. Onstatement is symbol (SYM) to simplify maintenance of the content spacespecification file 105 by reducing redundancy across noun spacedefinitions. Another statement is a filter statement that is used toclassify user stories, and to add information to output user stories. Inexemplary embodiments, each instance of statements as a group, defines asingle noun space. For example, the noun statement gives the noun spacea name, and the other verb, interface and platform statements providethe values for which each dimension is named.

As further described herein, a sym statement is a simple mechanism tocreate a short-hand for a list of values. The short-hand can then beused in defining noun spaces (e.g., in ‘noun’, ‘verb’, ‘ifc’, ‘platform’statements), in other sym statements, and in filter statements. Thisimplementation of sym statements therefore simplifies use and laterchanges to the content specification file since the list of relatedvalues can reliably changed throughout a set of specification files bychanging it in only a single place. For example, assume a content spacehas 15 noun spaces and 12 of those all use the same platform list. Thenthat list can defined once as a sym and that sym name used in the 12noun spaces. The example illustrates a group of related syms thataggregates various example platforms. The sym ‘all_email_env’ is thenused to in the definition of various noun spaces, for example in the‘draft email’ noun space.

The symbols that end in a trailing ‘_’ (underbar) are fold syms, as isthe ‘send_’. The ‘_’ indicates a symbol that can be folded. If therelevant type of value folding is requested (e.g. verb value to foldverb dimension, or platform value to fold platform dimension) then thesymbols marked with a trailing ‘_’ are folded. That is, the symbolitself is used in the content space when folded. If not folded thesymbol's value list is used in the content space. When folded a symbolis shown in generated user stories with the trailing ‘_’ so thateveryone seeing the user story will know it is folded (is anabstraction).

As further described herein, filter statements are used to classify userstories into one of five categories; n/a, future, nochange, changed ornew. They also can add to a story a variety of information. A filterstatement has the general structure: filter, <expression>,<classification>, <other requests>. The filter expression is a logicalexpression (i.e., evaluates to True or False) based on the language ofthe content the content space tool 110. For example, logical operatorsare supported (i.e., =, !=, >, <, in, not in, etc.) and the variablesallowed are ‘noun’, ‘verb’, ‘ifc’, ‘platform’ and defined symbols(sym's). Other keyword-value pairs which may be included in a filterstatement include but are not limited to: 1) Owner, owner name; 2) Groupor Groupby request; 3) Priority, priority value; 3) Testid, testidvalue; and 4) Tag, list of tag values. By default, filtering is doneafter all the content space specification files 105 have been read andafter folding is performed. The content space tool 110 has an option toturn off all filtering which is useful at time to check the results ofcontent space changes.

In exemplary embodiments, the content space specification files 105 canimplement additional statements, including, but not limited to: 1)comment_off—used to end commented-out block of lines; 2) comment_on—usedto start a block of comment lines. Starts skipping; 3) createdby—used toset the field ‘Created By’; 4) csvfile—sets the name of the output .csvfile; 5) eof—logically ends file early (rest of file skipped); 6)include—name a file to be included; 7) plannedfor—used to set the RTCfield ‘Planned For’; 8) scope—used to set filter scope to file (default)or global; 9) set_filterid_in_summaryfield—true or false (default); 10)set_implicit_folding—true or false (default); 11)set_summary_prefix—Default is “User Story”; 12)set_summary_suffix—Default is category of the user story; 13)tag_exclusion_set—Define a mutually exclusive set of tags; and 14)title—title (label) of content space.

As described herein, the specification files 105 support the definitionof symbols used in the defining the values and in the filters, that is,used within the content space specification file itself. This formathelps maintain a content space specification by lessening duplication ofconstants (i.e., dimension values). This format also serves to help thespecification file be self-documenting when description names are usedfor the symbols. For example, a list of platforms used in a priorrelease might be assigned to a symbol named ‘prior_platforms’. Thissymbol is then used in the noun spaces as a short-hand for the fulllist. This symbol can also be used in the filters.

Each use case in a content space is classified using filters into basiccategories including, but not limited to: not applicable, future,regression and development. “Not applicable” are use cases judged tolikely never be relevant for the product and future are use cases not inthe n+1 release but inherent in the content space. In exemplaryembodiments, the content space is identified to clearly encompass therequirements to help ensure nothing is missed. In doing so, some usecases are likely to be generated that are not planned for the currentrelease.

In exemplary embodiments, filters are also implemented to addinformation to the generated use cases. Examples of information that canbe added are priority, tags, references to requirements document and thelike.

In exemplary embodiments, filters are also implemented to cause sets ofuse cases to be grouped into a single, broader output use case.Implementing filters in this manner can be helpful in the caseregression use cases where fine-grained management and tracking of theindividual use cases is not necessary (e.g., due to the existence ofautomated testing built during previous releases).

In generating the agile use cases, one or more content spacespecification files 105 are read by the content space tool 110. Asdescribed herein, a primary output is the user story storage medium 115.In exemplary embodiments, the user story storage medium can have a commaseparated value (.csv) file format, which is a quasi-standard widelyused by many software applications. A second type of output is theadditional storage medium 120 for various summary and report likeinformation or in progress changes.

As described herein, content space data is embedded into a softwareproduct at block 330, which is now described in further detail. Inexemplary embodiments, the systems and methods described hereinimplement a content space represented internally, shippable and useableat run-time. In exemplary embodiments, a logical model of the contentspace is structured as a table.

The first four columns represent the four relevant coordinates of thecontent space: noun; verb; interface; and platform. The later columnscontain attributes associated with each row. Some attributes may be usedonly during development and test and eliminated in the generalavailability (GA) build of the content space jar. In the table, there isa row for each possible set of content space coordinate values at aselected resolution. The resolution is likely to vary over the course ofdevelopment and depends on the uses a particular product makes of theembedded content space and for new functions, how designs evolve andrelate to GUI design, and the like. As an example, platform values (themost complex of the dimensions) might represent value along thisspectrum; operating system, operating system with version, operatingsystem with version+hypervisor, operating system+version+hypervisiorwith version, and the like.

In exemplary embodiments, the content space resolution is also likely tovary within a given product release, as shipped, due to functional areasof complexity and implementation maturity. New user stories are likelyto need more detail that user stories from prior releases. For example,as an approximate, the number of rows for a average product might be asmuch as 1000. Physically the content space might be generated in JSONformat or as a csv file. For example a JSON file might be organized asfollows:

{ “noun”:{ “NOUN1”:{ “ifc”:[ “IFC1”, “IFC2”, ], “platform”:[“PLATFORM1”, “PLATFORM1” ], “verb”:[ “VERB1”, “VERB2” ] }, “NOUN2”:{“ifc”:[ “IFC1”, “IFC2”, ], “platform”:[ “PLATFORM1”, “PLATFORM1” ],“verb”:[ “VERB1”, “VERB2” ] }, } }

In exemplary embodiments, a hierarchical tree map is implemented torepresent content space on a browser. Each terminal node in the tree maprepresents a content space cell, while each internal node represents anaggregate of content space cells beneath it. The root node representsthe entire product offering. On a browser, if a user right clicks on anode, a drop down menu is displayed. For terminal node, each option inthe drop down menu corresponds to an attribute associated to the contentspace cell represented by the node. For example, the option of“InfoCenter” displays a link to the InfoCenter, which is the value ofthe attribute “InfoCenter”. For internal nodes, each option in the dropdown menu corresponds to either to an attribute associated to the foldedcontent space cell, or an aggregate of all attributes of cells beneathit. For example, the option of “InfoCenter” again displays a link to theInfoCenter, albeit at a higher level. The option of “Events” displaysall events related to the content space cells beneath the inner node.

In exemplary embodiments, the systems and methods described hereinimplement an internal interface for the software product's internalfunctional parts to access the content space at run time (e.g. aninternal callable set of interfaces that are used by product code). Thefollowing example interface methods show (in Java style) how variousfunctions and uses of the embedded content space can be achieved:

/** * Called by GUI code to determine what are allowed values for agiven * content space dimension. If a subset of allowed values cannot bedetermined, * return all possible values. * * The fast-path GUI codewill call this method repeatedly to eventually define * a target theuser wants to jump to. * * @param getcoordtype the coordinate typerequested. That is, which * coordinate type is needed; noun, verb orplatform. * @param target the set of coordinates which are selected sofar by * the user. * This method will be repeatedly called withundefined * or partially defined target values. * @param instance valueor list of values associated with the resource *  instance oftarget. * * @return list of allowed coordinate values for requested *dimension. * */ public List<String> getlistCScoordinate( CScoordgetcoordtype, CScoord target, string instance ); /** * * The fast-pathGUI code will call this method (repeatedly) and enable * the Go! buttonwhen exactly 1 panel is returned. * * @param target the set ofcoordinates which are desired by the user. * This method will berepeatedly called with undefined * or partially defined targetvalues. * * @param instance NULL or value or list of values associatedwith the * target. * * @return the 0 or more GUI panels (names or IDs?)which are valid. * */ public List<GUIpanel> getGUIpanel( CScoord target,string instance ); /** * Given valid content space coordinates and thename of CS attribute, * return that attribute value. * * @param coord CScoordinates (1 valid set) * @param at name of CS attribute * * @returnattribute value */ public String getCSattribute( CScoord coord,CSattribute at ); /** * Set an content space attribute value. Someattributes are * read-only. * * @param coord CS coordinates (1 validset) * @param at name of CS attribute * @param atvalue new value ifsuccessful * * @return success or fail */ public ReturnCodesetCSattribute( CScoord coord, CSattribute at, String atvalue ); /** *Get profile about the embedded content space, or a subset. To * selectsubset, the param coord is used as a filter (some coord * values arewild-cards). Returns a list of the matching user * stories and profiledata for each. * * @param coord CS coordinates * * @return returnsexecution profile data for each user story in the * region of the CSselected by coord. * * If coord NULL or all *, the returned data * scopeis for the entire content space. * * - number times executed * - numberof failed executions * - average duration * - date & time of last reset*/ public List<String> getCSprofiledata( CScoord coord ); /** * Resetprofile data to zeros for the specified region. * * @param coord CScoordinates, optional. * * @return success or fail */ public BooleanresetCSprofiledata( CScoord coord ); public enum CSstatus { started,updated, done_ok, done_err } /** * Mark user story active, for aspecific (caller's) thread, based * values set in parm. Note that whenstatus is marked with a * completion value, the runtime attribute numberfor the * story are updated. * * Taskid and thread id are use to helpensure uniqueness for * product unit of work. * * * @param coord CScoordinates * @param taskid Task id * @param Long threadid thread idwith which the user story is * associated. * @param status enum ofstatus to be set for the story. * */ public void markCSstory( CScoordcoord, Long, taskid, Long threadid, CSstatus status ); /** * Get userstory for an associated task, thread. If a CS story does * not exist,return null. Used for logging, trace and FFDC. * * @param Long taskidtask id of requested * @param Long threadid thread id of requested * *@return CScoord (content space coordinates for the thread) */ publicCScoord getCSstory( Long task, Long tid );

In exemplary embodiments, the systems and methods described hereinfurther obtain and set attributes to each cell in the content space. Theattributes are used for various purposes by the run-time functionsaccess content space. Some example attributes include, but are notlimited to: 1) cell category; 2) cell requirements; 3) developmentowner; 4) test owner; 5) graphical user interface (GUI) panel ID; 6)instances needed, and the like.

During product development time, people with different roles can attachattributes to each content space cell. Each attribute consists of a nameand a value, both are of a String type in Java programming language, forexample. FIGS. 4A and 4B illustrate an example of a table 400 thatillustrates the attributes that can be attached to each cell inaccordance with exemplary embodiments. It will be appreciated that thereare other attributes contemplated in other embodiments. The attributesshown in the table 400 are just some of the content space cellattributes proposed to be shipped with a product for use at run-time.The table 400 represents a subset of attributes associated with contentspace cells.

In exemplary embodiments, the following logical information is likelystored in memory (rather than a file like the runtime content spacedata) and might be located in the task (or thread) context datatypically created at the external interface layers and passed down ascalls are made. This data is filled in via multiple calls to the profileinterfaces above, one row per unique taskid+threadid ‘key’:

. . . . . . . . . . . . . . . . . . . . . . . . . . . taskid threadidnoun verb interface platform status start complete value . . . . . . . .. . . . . . . . . . . . . . . . . . .

In exemplary embodiments, the systems and methods described hereinfurther integrate a run-time content space within a normal softwareproduct build process. The Content Space specification (e.g., thespecification files 105) can be saved in JavaScript Object Notation(JSON) format in a plain text file. This file is copied into a jar(e.g., a Java Archive) file, which is included in the final installationpackage. During installation process, the jar file is installed to anappropriate location on the machine.

In exemplary embodiments, the systems and methods described hereinupdate the content space definition within the software product afterthe software is installed (similar to updating other components of thesoftware product). With each patch of the software product, comes apotentially updated content space specification document. When a patchis installed, the jar that contains the new content space specificationdocument is copied to the correct location on the machine, overridingthe previous content space document. This process ensures the latestcontent space specification is available to all exploiters. In exemplaryembodiments, the profile information can be persevered in the oldcontent space document, and merged into the new document. The historicaldata collected during the life time of the old content space documentwill not be lost with this approach.

The content space embedding and other content space implementationsdescribed herein can be performed in any suitable computing system asnow described. FIG. 5 illustrates an exemplary embodiment of a system500 in which content space embedding can be implemented. The methodsdescribed herein can be implemented in software (e.g., firmware),hardware, or a combination thereof. In exemplary embodiments, themethods described herein are implemented in software, as an executableprogram, and is executed by a special or general-purpose digitalcomputer, such as a personal computer, workstation, minicomputer, ormainframe computer. The system 500 therefore includes general-purposecomputer 501.

In exemplary embodiments, in terms of hardware architecture, as shown inFIG. 5, the computer 501 includes a processor 505, memory 510 coupled toa memory controller 515, and one or more input and/or output (I/O)devices 540, 545 (or peripherals) that are communicatively coupled via alocal input/output controller 535. The input/output controller 535 canbe, but is not limited to, one or more buses or other wired or wirelessconnections, as is known in the art. The input/output controller 535 mayhave additional elements, which are omitted for simplicity, such ascontrollers, buffers (caches), drivers, repeaters, and receivers, toenable communications. Further, the local interface may include address,control, and/or data connections to enable appropriate communicationsamong the aforementioned components.

The processor 505 is a hardware device for executing software,particularly that stored in memory 510. The processor 505 can be anycustom made or commercially available processor, a central processingunit (CPU), an auxiliary processor among several processors associatedwith the computer 501, a semiconductor based microprocessor (in the formof a microchip or chip set), a macroprocessor, or generally any devicefor executing software instructions.

The memory 510 can include any one or combination of volatile memoryelements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM,etc.)) and nonvolatile memory elements (e.g., ROM, erasable programmableread only memory (EPROM), electronically erasable programmable read onlymemory (EEPROM), programmable read only memory (PROM), tape, compactdisc read only memory (CD-ROM), disk, diskette, cartridge, cassette orthe like, etc.). Moreover, the memory 510 may incorporate electronic,magnetic, optical, and/or other types of storage media. Note that thememory 510 can have a distributed architecture, where various componentsare situated remote from one another, but can be accessed by theprocessor 505.

The software in memory 510 may include one or more separate programs,each of which comprises an ordered listing of executable instructionsfor implementing logical functions. In the example of FIG. 5, thesoftware in the memory 510 includes the content space embedding methodsdescribed herein in accordance with exemplary embodiments and a suitableoperating system (OS) 511. The OS 511 essentially controls the executionof other computer programs, such the content space embedding systems andmethods as described herein, and provides scheduling, input-outputcontrol, file and data management, memory management, and communicationcontrol and related services.

The content space embedding methods described herein may be in the formof a source program, executable program (object code), script, or anyother entity comprising a set of instructions to be performed. When asource program, then the program needs to be translated via a compiler,assembler, interpreter, or the like, which may or may not be includedwithin the memory 510, so as to operate properly in connection with theOS 511. Furthermore, the content space embedding methods can be writtenas an object oriented programming language, which has classes of dataand methods, or a procedure programming language, which has routines,subroutines, and/or functions.

In exemplary embodiments, a conventional keyboard 550 and mouse 555 canbe coupled to the input/output controller 535. Other output devices suchas the I/O devices 540, 545 may include input devices, for example butnot limited to a printer, a scanner, microphone, and the like. Finally,the I/O devices 540, 545 may further include devices that communicateboth inputs and outputs, for instance but not limited to, a networkinterface card (NIC) or modulator/demodulator (for accessing otherfiles, devices, systems, or a network), a radio frequency (RF) or othertransceiver, a telephonic interface, a bridge, a router, and the like.The system 500 can further include a display controller 525 coupled to adisplay 530. In exemplary embodiments, the system 500 can furtherinclude a network interface 560 for coupling to a network 565. Thenetwork 565 can be an IP-based network for communication between thecomputer 501 and any external server, client and the like via abroadband connection. The network 565 transmits and receives databetween the computer 501 and external systems. In exemplary embodiments,network 565 can be a managed IP network administered by a serviceprovider. The network 565 may be implemented in a wireless fashion,e.g., using wireless protocols and technologies, such as WiFi, WiMax,etc. The network 565 can also be a packet-switched network such as alocal area network, wide area network, metropolitan area network,Internet network, or other similar type of network environment. Thenetwork 565 may be a fixed wireless network, a wireless local areanetwork (LAN), a wireless wide area network (WAN) a personal areanetwork (PAN), a virtual private network (VPN), intranet or othersuitable network system and includes equipment for receiving andtransmitting signals.

If the computer 501 is a PC, workstation, intelligent device or thelike, the software in the memory 510 may further include a basic inputoutput system (BIOS) (omitted for simplicity). The BIOS is a set ofessential software routines that initialize and test hardware atstartup, start the OS 511, and support the transfer of data among thehardware devices. The BIOS is stored in ROM so that the BIOS can beexecuted when the computer 501 is activated.

When the computer 501 is in operation, the processor 505 is configuredto execute software stored within the memory 510, to communicate data toand from the memory 510, and to generally control operations of thecomputer 501 pursuant to the software. The content space embeddingmethods described herein and the OS 511, in whole or in part, buttypically the latter, are read by the processor 505, perhaps bufferedwithin the processor 505, and then executed.

When the systems and methods described herein are implemented insoftware, as is shown in FIG. 5, the methods can be stored on anycomputer readable medium, such as storage 520, for use by or inconnection with any computer related system or method.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), an optical fiber,a portable compact disc read-only memory (CD-ROM), an optical storagedevice, a magnetic storage device, or any suitable combination of theforegoing. In the context of this document, a computer readable storagemedium may be any tangible medium that can contain, or store a programfor use by or in connection with an instruction execution system,apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wireline, optical fiber cable, RF, etc., or any suitable combination ofthe foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++ or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a local area network (LAN) or awide area network (WAN), or the connection may be made to an externalcomputer (for example, through the Internet using an Internet ServiceProvider).

Aspects of the present invention are described below with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, or other devices to causea series of operational steps to be performed on the computer, otherprogrammable apparatus or other devices to produce a computerimplemented process such that the instructions which execute on thecomputer or other programmable apparatus provide processes forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

In exemplary embodiments, where the content space embedding methods areimplemented in hardware, the content space embedding methods describedherein can implemented with any or a combination of the followingtechnologies, which are each well known in the art: a discrete logiccircuit(s) having logic gates for implementing logic functions upon datasignals, an application specific integrated circuit (ASIC) havingappropriate combinational logic gates, a programmable gate array(s)(PGA), a field programmable gate array (FPGA), etc.

Technical effects include the ability to generate user stories in acontent space that can be embedded in a software product. The contentspace is then available for product level use at runtime, and in thecontent of a product build.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of onemore other features, integers, steps, operations, element components,and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present invention has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the invention in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the invention. Theembodiment was chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated

The flow diagrams depicted herein are just one example. There may bemany variations to this diagram or the steps (or operations) describedtherein without departing from the spirit of the invention. Forinstance, the steps may be performed in a differing order or steps maybe added, deleted or modified. All of these variations are considered apart of the claimed invention.

While exemplary embodiments of the invention have been described, itwill be understood that those skilled in the art, both now and in thefuture, may make various improvements and enhancements which fall withinthe scope of the claims which follow. These claims should be construedto maintain the proper protection for the invention first described.

What is claimed is:
 1. A computer-implemented method for generating userstories for a software product, the method comprising: collecting, by aprocessor, a plurality of requirements; creating, by the processor, aplurality of content space specification files that includes theplurality of requirements; processing, by the processor, the pluralityof content space specification files to generate the user stories;defining, by the processor, a content space; embedding, by theprocessor, the content space in the software product.
 2. The method asclaimed in claim 1 further comprising outputting, by the processor, theuser stories.
 3. The method as claimed in claim 1 wherein processing theplurality of content space specification files comprises identifyingcontent space specification statements in each of the plurality ofcontent space specification files.
 4. The method as claimed in claim 2further comprising traversing, by the processor, the content space togenerate the user stories.
 5. The method as claimed in claim 4 whereinthe content space includes a plurality of cells, each of the pluralityof cells corresponding to one of the user stories, each of the pluralityof cells having multiple dimensions, each of the multiple dimensionshaving one or more values.
 6. The method as claimed in claim 5 whereinthe multiple dimensions include a noun dimension.
 7. The method asclaimed in claim 6 wherein traversing the content space comprises: foreach of the noun dimensions, for each of the plurality of cells:traversing, by the processor, other dimensions of the multipledimensions of the cell, one value at a time, to generate the user storycorresponding to the cell.
 8. The method as claimed in claim 2 furthercomprising grouping, by the processor, the content space.
 9. The methodas claimed in claim 2 further comprising folding, by the processor, thecontent space.
 10. A computer program product for generating userstories for a software product, the computer program product including anon-transitory computer readable medium storing instructions for causinga computer to implement a method, the method comprising: collecting, bya processor, a plurality of requirements; creating, by the processor, aplurality of content space specification files that includes theplurality of requirements; processing, by the processor, the pluralityof content space specification files to generate the user stories;defining, by the processor, a content space; embedding, by theprocessor, the content space in the software product.
 11. The computerprogram product as claimed in claim 10, wherein the method furthercomprises outputting the user stories.
 12. The computer program productas claimed in claim 10 wherein processing the plurality of content spacespecification files comprises identifying content space specificationstatements in each of the plurality of content space specificationfiles.
 13. The computer program product as claimed in claim 11, whereinthe method further comprises traversing the content space to generatethe user stories.
 14. The computer program product as claimed in claim13 wherein the content space includes a plurality of cells, each of theplurality of cells corresponding to each of the user stories, each ofthe plurality of cells having multiple dimensions, each of the multipledimensions having one or more values.
 15. The computer program productas claimed in claim 14 wherein the multiple dimensions include a noundimension.
 16. The computer program product as claimed in claim 15wherein traversing the content space comprises for each of the noundimensions, for each of the plurality of cells: traversing, by theprocessor, other dimensions of the multiple dimensions of the cell, onevalue at a time, to generate the user story corresponding to the cell.17. The computer program product as claimed in claim 11, wherein themethod further comprises grouping the content space.
 18. The computerprogram product as claimed in claim 11, wherein the method furthercomprises folding the content space.
 19. A system for generating userstories for a software product, the system comprising: a processorconfigured to: collect a plurality of requirements; create a pluralityof content space specification files that includes the plurality ofrequirements; process the plurality of content space specification filesto generate the user stories; define a content space; embed the contentspace in the software product; and output the user stories.
 20. Acomputer-implemented method for generating user stories for a softwareproduct, the method comprising: collecting a plurality of requirements;defining a content space including a plurality of cells, each celldefining an agile story, each cell having a plurality of dimensions;creating a plurality of content space specification files that includesthe plurality of requirements; defining a content space; traversing atleast one dimension of each of the plurality of cells to generate a userstory; embedding the content space in the software product; andgenerating reports defining each of the user stories.